Method and apparatus for system information delivery in advanced wireless systems

ABSTRACT

A method of user equipment (UE) for system information transmission in a wireless communication system is provided. The method comprises receiving, from a base station (BS), a synchronization signal/physical broadcasting channel (SS/PBCH) block comprising a PBCH that carries a master information block (MIB) including an SIB1 CORESET configuration, wherein the SIB1 CORESET configuration comprises a frequency location, a number of resource blocks (RBs) comprising an SIB1 CORESET associated with the SS/PBCH block, and information of time domain resources of the SIB1 CORESET, determining an initial active bandwidth part (BWP) comprising the frequency location, the number of RBs comprising the SIB1 CORESET, and a numerology of remaining minimum system information (RMSI), and receiving, from the BS, a physical downlink control channel (PDCCH) mapped to at least one time-frequency resource within the SIB1 CORESET, wherein the PDCCH includes scheduling information of a physical downlink shared channel (PDSCH) containing an SIB 1.

CROSS-REFERENCE TO RELATED APPLICATIONS AND CLAIM OF PRIORITY

The present application claims priority to U.S. Provisional PatentApplication Ser. No. 62/442,237, filed on Jan. 4, 2017; U.S. ProvisionalPatent Application Ser. No. 62/507,924, filed on May 18, 2017; U.S.Provisional Patent Application Ser. No. 62/520,235, filed on Jun. 15,2017; and U.S. Provisional Patent Application Ser. No. 62/556,293, filedon Sep. 8, 2017. The content of the above-identified patent document isincorporated herein by reference.

TECHNICAL FIELD

The present application relates generally to system information deliveryin wireless communication systems. More specifically, this disclosurerelates to system information block delivery and acquisition in nextgeneration wireless communication systems.

BACKGROUND

5th generation (5G) mobile communications, initial commercialization ofwhich is expected around 2020, is recently gathering increased momentumwith all the worldwide technical activities on the various candidatetechnologies from industry and academia. The candidate enablers for the5G mobile communications include massive antenna technologies, fromlegacy cellular frequency bands up to high frequencies, to providebeamforming gain and support increased capacity, new waveform (e.g., anew radio access technology (RAT)) to flexibly accommodate variousservices/applications with different requirements, new multiple accessschemes to support massive connections, and so on. The InternationalTelecommunication Union (ITU) has categorized the usage scenarios forinternational mobile telecommunications (IMT) for 2020 and beyond into 3main groups such as enhanced mobile broadband, massive machine typecommunications (MTC), and ultra-reliable and low latency communications.In addition, the ITC has specified target requirements such as peak datarates of 20 gigabit per second (Gb/s), user experienced data rates of100 megabit per second (Mb/s), a spectrum efficiency improvement of 3X,support for up to 500 kilometer per hour (km/h) mobility, 1 millisecond(ms) latency, a connection density of 106 devices/km2, a network energyefficiency improvement of 100× and an area traffic capacity of 10Mb/s/m2. While all the requirements need not be met simultaneously, thedesign of 5G networks may provide flexibility to support variousapplications meeting part of the above requirements on a use case basis.

SUMMARY

The present disclosure relates to a pre-5th-Generation (5G) or 5Gcommunication system to be provided for supporting higher data ratesbeyond 4th-Generation (4G) communication system such as long termevolution (LTE). Embodiments of the present disclosure provide multipleservices in advanced communication systems.

In one embodiment, a user equipment (UE) for system informationtransmission in a wireless communication system is provided. The UEcomprises a transceiver configured to receive, from a base station (BS),a synchronization signal/physical broadcasting channel (SS/PBCH) blockcomprising a PBCH that carries a master information block (MIB)including an SIB1 CORESET configuration, wherein the SIB1 CORESETconfiguration comprises a frequency location, a number of resourceblocks (RBs) comprising an SIB1 CORESET associated with the SS/PBCHblock, and information of time domain resources of the SIB1 CORESET. TheUE further comprises a processor configured to determine an initialactive bandwidth part (BWP) comprising the frequency location, thenumber of RBs comprising the SIB1 CORESET, and a numerology of remainingminimum system information (RMSI). The UE further comprises thetransceiver configured to receive, from the BS, a physical downlinkcontrol channel (PDCCH) mapped to at least one time-frequency resourcewithin the SIB1 CORESET, wherein the PDCCH includes schedulinginformation of a physical downlink shared channel (PDSCH) containing anSIB 1.

In another embodiment, a BS for system information transmission in awireless communication system is provided. The BS comprises a processorconfigured to determine an initial active BWP comprising a frequencylocation, a number of RBs comprising a SIB1 CORESET, and a numerology ofRMSI. The BS further comprises a transceiver configured to transmit, toa UE, a SS/PBCH block comprising a PBCH that carries a MIB including anSIB1 CORESET configuration, wherein the SIB1 CORESET configurationcomprises a frequency location, a number of RBs comprising an SIB1CORESET associated with the SS/PBCH block, and information of timedomain resources of the SIB1 CORESET, and transmit a PDCCH mapped to atleast one time-frequency resource within the SIB1 CORESET, wherein thePDCCH includes scheduling information of a PDSCH containing an SIB 1.

In yet another embodiment, a method of a UE for system informationtransmission in a wireless communication system is provided. The methodcomprises receiving, from a BS, a SS/PBCH block comprising a PBCH thatcarries a MIB including an SIB1 CORESET configuration, wherein the SIB1CORESET configuration comprises a frequency location, a number of RBscomprising an SIB 1 CORESET associated with the SS/PBCH block, andinformation of time domain resources of the SIB1 CORESET, determining aninitial active BWP comprising the frequency location, the number of RBscomprising the SIB1 CORESET, and a numerology of RMSI, receiving, fromthe BS, a PDCCH mapped to at least one time-frequency resource withinthe SIB1 CORESET, wherein the PDCCH includes scheduling information of aPDSCH containing an SIB 1.

Other technical features may be readily apparent to one skilled in theart from the following figures, descriptions, and claims.

Before undertaking the DETAILED DESCRIPTION below, it may beadvantageous to set forth definitions of certain words and phrases usedthroughout this patent document. The term “couple” and its derivativesrefer to any direct or indirect communication between two or moreelements, whether or not those elements are in physical contact with oneanother. The terms “transmit,” “receive,” and “communicate,” as well asderivatives thereof, encompass both direct and indirect communication.The terms “include” and “comprise,” as well as derivatives thereof, meaninclusion without limitation. The term “or” is inclusive, meaningand/or. The phrase “associated with,” as well as derivatives thereof,means to include, be included within, interconnect with, contain, becontained within, connect to or with, couple to or with, be communicablewith, cooperate with, interleave, juxtapose, be proximate to, be boundto or with, have, have a property of, have a relationship to or with, orthe like. The term “controller” means any device, system or part thereofthat controls at least one operation. Such a controller may beimplemented in hardware or a combination of hardware and software and/orfirmware. The functionality associated with any particular controllermay be centralized or distributed, whether locally or remotely. Thephrase “at least one of,” when used with a list of items, means thatdifferent combinations of one or more of the listed items may be used,and only one item in the list may be needed. For example, “at least oneof: A, B, and C” includes any of the following combinations: A, B, C, Aand B, A and C, B and C, and A and B and C.

Moreover, various functions described below can be implemented orsupported by one or more computer programs, each of which is formed fromcomputer readable program code and embodied in a computer readablemedium. The terms “application” and “program” refer to one or morecomputer programs, software components, sets of instructions,procedures, functions, objects, classes, instances, related data, or aportion thereof adapted for implementation in a suitable computerreadable program code. The phrase “computer readable program code”includes any type of computer code, including source code, object code,and executable code. The phrase “computer readable medium” includes anytype of medium capable of being accessed by a computer, such as readonly memory (ROM), random access memory (RAM), a hard disk drive, acompact disc (CD), a digital video disc (DVD), or any other type ofmemory. A “non-transitory” computer readable medium excludes wired,wireless, optical, or other communication links that transporttransitory electrical or other signals. A non-transitory computerreadable medium includes media where data can be permanently stored andmedia where data can be stored and later overwritten, such as arewritable optical disc or an erasable memory device.

Definitions for other certain words and phrases are provided throughoutthis patent document. Those of ordinary skill in the art shouldunderstand that in many if not most instances, such definitions apply toprior as well as future uses of such defined words and phrases.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsadvantages, reference is now made to the following description taken inconjunction with the accompanying drawings, in which like referencenumerals represent like parts:

FIG. 1 illustrates an example wireless network according to embodimentsof the present disclosure;

FIG. 2 illustrates an example eNB according to embodiments of thepresent disclosure;

FIG. 3 illustrates an example UE according to embodiments of the presentdisclosure;

FIG. 4A illustrates an example high-level diagram of an orthogonalfrequency division multiple access transmit path according toembodiments of the present disclosure;

FIG. 4B illustrates an example high-level diagram of an orthogonalfrequency division multiple access receive path according to embodimentsof the present disclosure;

FIG. 5 illustrates an example network slicing according to embodimentsof the present disclosure;

FIG. 6 illustrates an example number of digital chains according toembodiments of the present disclosure;

FIG. 7 illustrates an example system information block transmissionaccording to embodiments of the present disclosure;

FIG. 8 illustrates an example SS block transmission according toembodiments of the present disclosure;

FIG. 9 illustrates an example RMSI transmission according to embodimentsof the present disclosure;

FIG. 10 illustrates an example RBG transmission according to embodimentsof the present disclosure;

FIG. 11 illustrates an example CORESET transmission in continuous anddistributed mapping according to embodiments of the present disclosure;and

FIG. 12 illustrates a flow chart of a method for system informationdelivery according to embodiments of the present disclosure.

DETAILED DESCRIPTION

FIG. 1 through FIG. 12, discussed below, and the various embodimentsused to describe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way to limit the scope of the disclosure. Those skilled in the artwill understand that the principles of the present disclosure may beimplemented in any suitably arranged system or device.

The following documents are hereby incorporated by reference into thepresent disclosure as if fully set forth herein: 3GPP TS 36.211 v13.0.0,“E-UTRA, Physical channels and modulation;” 3GPP TS 36.212 v13.0.0,“E-UTRA, Multiplexing and Channel coding;” 3GPP TS 36.213 v13.0.0,“E-UTRA, Physical Layer Procedures;” and 3GPP TS 36.331 v13.0.0,“E-UTRA, Radio Resource Control (RRC) Protocol Specification.”

To meet the demand for wireless data traffic having increased sincedeployment of 4G communication systems, efforts have been made todevelop an improved 5G or pre-5G communication system. Therefore, the 5Gor pre-5G communication system is also called a “beyond 4G network” or a“post LTE system.”

The 5G communication system is considered to be implemented in higherfrequency (mmWave) bands, e.g., 60 GHz bands, so as to accomplish higherdata rates. To decrease propagation loss of the radio waves and increasethe transmission coverage, the beamforming, massive multiple-inputmultiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna,an analog beam forming, large scale antenna techniques and the like arediscussed in 5G communication systems.

In addition, in 5G communication systems, development for system networkimprovement is under way based on advanced small cells, cloud radioaccess networks (RANs), ultra-dense networks, device-to-device (D2D)communication, wireless backhaul communication, moving network,cooperative communication, coordinated multi-points (CoMP) transmissionand reception, interference mitigation and cancellation and the like.

In the 5G system, hybrid frequency shift keying and quadrature amplitudemodulation (FQAM) and sliding window superposition coding (SWSC) as anadaptive modulation and coding (AMC) technique, and filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse codemultiple access (SCMA) as an advanced access technology have beendeveloped.

FIGS. 1-4B below describe various embodiments implemented in wirelesscommunications systems and with the use of orthogonal frequency divisionmultiplexing (OFDM) or orthogonal frequency division multiple access(OFDMA) communication techniques. The descriptions of FIGS. 1-3 are notmeant to imply physical or architectural limitations to the manner inwhich different embodiments may be implemented. Different embodiments ofthe present disclosure may be implemented in any suitably-arrangedcommunications system.

FIG. 1 illustrates an example wireless network according to embodimentsof the present disclosure. The embodiment of the wireless network shownin FIG. 1 is for illustration only. Other embodiments of the wirelessnetwork 100 could be used without departing from the scope of thisdisclosure.

As shown in FIG. 1, the wireless network includes an eNB 101, an eNB102, and an eNB 103. The eNB 101 communicates with the eNB 102 and theeNB 103. The eNB 101 also communicates with at least one network 130,such as the Internet, a proprietary Internet Protocol (IP) network, orother data network.

The eNB 102 provides wireless broadband access to the network 130 for afirst plurality of UEs within a coverage area 120 of the eNB 102. Thefirst plurality of UEs includes a UE 111, which may be located in asmall business (SB); a UE 112, which may be located in an enterprise(E); a UE 113, which may be located in a WiFi hotspot (HS); a UE 114,which may be located in a first residence (R); a UE 115, which may belocated in a second residence (R); and a UE 116, which may be a mobiledevice (M), such as a cell phone, a wireless laptop, a wireless PDA, orthe like. The eNB 103 provides wireless broadband access to the network130 for a second plurality of UEs within a coverage area 125 of the eNB103. The second plurality of UEs includes the UE 115 and the UE 116. Insome embodiments, one or more of the eNBs 101-103 may communicate witheach other and with the UEs 111-116 using 5G, LTE, LTE-A, WiMAX, WiFi,or other wireless communication techniques.

Depending on the network type, the term “base station” or “BS” can referto any component (or collection of components) configured to providewireless access to a network, such as transmit point (TP),transmit-receive point (TRP), an enhanced base station (eNodeB or eNB),a 5G base station (gNB), a macrocell, a femtocell, a WiFi access point(AP), or other wirelessly enabled devices. Base stations may providewireless access in accordance with one or more wireless communicationprotocols, e.g., 5G 3GPP new radio interface/access (NR), long termevolution (LTE), LTE advanced (LTE-A), high speed packet access (HSPA),Wi-Fi 802.11a/b/g/n/ac, etc. For the sake of convenience, the terms “BS”and “TRP” are used interchangeably in this patent document to refer tonetwork infrastructure components that provide wireless access to remoteterminals. Also, depending on the network type, the term “userequipment” or “UE” can refer to any component such as “mobile station,”“subscriber station,” “remote terminal,” “wireless terminal,” “receivepoint,” or “user device.” For the sake of convenience, the terms “userequipment” and “UE” are used in this patent document to refer to remotewireless equipment that wirelessly accesses a BS, whether the UE is amobile device (such as a mobile telephone or smartphone) or is normallyconsidered a stationary device (such as a desktop computer or vendingmachine).

Dotted lines show the approximate extents of the coverage areas 120 and125, which are shown as approximately circular for the purposes ofillustration and explanation only. It should be clearly understood thatthe coverage areas associated with eNBs, such as the coverage areas 120and 125, may have other shapes, including irregular shapes, dependingupon the configuration of the eNBs and variations in the radioenvironment associated with natural and man-made obstructions.

As described in more detail below, one or more of the UEs 111-116include circuitry, programming, or a combination thereof, for systeminformation delivery in an advanced wireless communication system. Incertain embodiments, and one or more of the eNBs 101-103 includescircuitry, programming, or a combination thereof, for efficient systeminformation delivery in an advanced wireless communication system.

Although FIG. 1 illustrates one example of a wireless network, variouschanges may be made to FIG. 1. For example, the wireless network couldinclude any number of eNBs and any number of UEs in any suitablearrangement. Also, the eNB 101 could communicate directly with anynumber of UEs and provide those UEs with wireless broadband access tothe network 130. Similarly, each eNB 102-103 could communicate directlywith the network 130 and provide UEs with direct wireless broadbandaccess to the network 130. Further, the eNBs 101, 102, and/or 103 couldprovide access to other or additional external networks, such asexternal telephone networks or other types of data networks.

FIG. 2 illustrates an example eNB 102 according to embodiments of thepresent disclosure. The embodiment of the eNB 102 illustrated in FIG. 2is for illustration only, and the eNBs 101 and 103 of FIG. 1 could havethe same or similar configuration. However, eNBs come in a wide varietyof configurations, and FIG. 2 does not limit the scope of thisdisclosure to any particular implementation of an eNB.

As shown in FIG. 2, the eNB 102 includes multiple antennas 205 a-205 n,multiple RF transceivers 210 a-210 n, transmit (TX) processing circuitry215, and receive (RX) processing circuitry 220. The eNB 102 alsoincludes a controller/processor 225, a memory 230, and a backhaul ornetwork interface 235.

The RF transceivers 210 a-210 n receive, from the antennas 205 a-205 n,incoming RF signals, such as signals transmitted by UEs in the network100. The RF transceivers 210 a-210 n down-convert the incoming RFsignals to generate IF or baseband signals. The IF or baseband signalsare sent to the RX processing circuitry 220, which generates processedbaseband signals by filtering, decoding, and/or digitizing the basebandor IF signals. The RX processing circuitry 220 transmits the processedbaseband signals to the controller/processor 225 for further processing.

The TX processing circuitry 215 receives analog or digital data (such asvoice data, web data, e-mail, or interactive video game data) from thecontroller/processor 225. The TX processing circuitry 215 encodes,multiplexes, and/or digitizes the outgoing baseband data to generateprocessed baseband or IF signals. The RF transceivers 210 a-210 nreceive the outgoing processed baseband or IF signals from the TXprocessing circuitry 215 and up-converts the baseband or IF signals toRF signals that are transmitted via the antennas 205 a-205 n.

The controller/processor 225 can include one or more processors or otherprocessing devices that control the overall operation of the eNB 102.For example, the controller/processor 225 could control the reception offorward channel signals and the transmission of reverse channel signalsby the RF transceivers 210 a-210 n, the RX processing circuitry 220, andthe TX processing circuitry 215 in accordance with well-knownprinciples. The controller/processor 225 could support additionalfunctions as well, such as more advanced wireless communicationfunctions. For instance, the controller/processor 225 could support beamforming or directional routing operations in which outgoing signals frommultiple antennas 205 a-205 n are weighted differently to effectivelysteer the outgoing signals in a desired direction. Any of a wide varietyof other functions could be supported in the eNB 102 by thecontroller/processor 225.

The controller/processor 225 is also capable of executing programs andother processes resident in the memory 230, such as an OS. Thecontroller/processor 225 can move data into or out of the memory 230 asrequired by an executing process.

The controller/processor 225 is also coupled to the backhaul or networkinterface 235. The backhaul or network interface 235 allows the eNB 102to communicate with other devices or systems over a backhaul connectionor over a network. The interface 235 could support communications overany suitable wired or wireless connection(s). For example, when the eNB102 is implemented as part of a cellular communication system (such asone supporting 5G, LTE, or LTE-A), the interface 235 could allow the eNB102 to communicate with other eNBs over a wired or wireless backhaulconnection. When the eNB 102 is implemented as an access point, theinterface 235 could allow the eNB 102 to communicate over a wired orwireless local area network or over a wired or wireless connection to alarger network (such as the Internet). The interface 235 includes anysuitable structure supporting communications over a wired or wirelessconnection, such as an Ethernet or RF transceiver.

The memory 230 is coupled to the controller/processor 225. Part of thememory 230 could include a RAM, and another part of the memory 230 couldinclude a Flash memory or other ROM.

Although FIG. 2 illustrates one example of eNB 102, various changes maybe made to FIG. 2. For example, the eNB 102 could include any number ofeach component shown in FIG. 2. As a particular example, an access pointcould include a number of interfaces 235, and the controller/processor225 could support routing functions to route data between differentnetwork addresses. As another particular example, while shown asincluding a single instance of TX processing circuitry 215 and a singleinstance of RX processing circuitry 220, the eNB 102 could includemultiple instances of each (such as one per RF transceiver). Also,various components in FIG. 2 could be combined, further subdivided, oromitted and additional components could be added according to particularneeds.

FIG. 3 illustrates an example UE 116 according to embodiments of thepresent disclosure. The embodiment of the UE 116 illustrated in FIG. 3is for illustration only, and the UEs 111-115 of FIG. 1 could have thesame or similar configuration. However, UEs come in a wide variety ofconfigurations, and FIG. 3 does not limit the scope of this disclosureto any particular implementation of a UE.

As shown in FIG. 3, the UE 116 includes an antenna 305, a radiofrequency (RF) transceiver 310, TX processing circuitry 315, amicrophone 320, and receive (RX) processing circuitry 325. The UE 116also includes a speaker 330, a processor 340, an input/output (I/O)interface (IF) 345, a touchscreen 350, a display 355, and a memory 360.The memory 360 includes an operating system (OS) 361 and one or moreapplications 362.

The RF transceiver 310 receives, from the antenna 305, an incoming RFsignal transmitted by an eNB of the network 100. The RF transceiver 310down-converts the incoming RF signal to generate an intermediatefrequency (IF) or baseband signal. The IF or baseband signal is sent tothe RX processing circuitry 325, which generates a processed basebandsignal by filtering, decoding, and/or digitizing the baseband or IFsignal. The RX processing circuitry 325 transmits the processed basebandsignal to the speaker 330 (such as for voice data) or to the processor340 for further processing (such as for web browsing data).

The TX processing circuitry 315 receives analog or digital voice datafrom the microphone 320 or other outgoing baseband data (such as webdata, e-mail, or interactive video game data) from the processor 340.The TX processing circuitry 315 encodes, multiplexes, and/or digitizesthe outgoing baseband data to generate a processed baseband or IFsignal. The RF transceiver 310 receives the outgoing processed basebandor IF signal from the TX processing circuitry 315 and up-converts thebaseband or IF signal to an RF signal that is transmitted via theantenna 305.

The processor 340 can include one or more processors or other processingdevices and execute the OS 361 stored in the memory 360 in order tocontrol the overall operation of the UE 116. For example, the processor340 could control the reception of forward channel signals and thetransmission of reverse channel signals by the RF transceiver 310, theRX processing circuitry 325, and the TX processing circuitry 315 inaccordance with well-known principles. In some embodiments, theprocessor 340 includes at least one microprocessor or microcontroller.

The processor 340 is also capable of executing other processes andprograms resident in the memory 360, such as processes for systeminformation delivery in an advanced wireless communication system. Theprocessor 340 can move data into or out of the memory 360 as required byan executing process. In some embodiments, the processor 340 isconfigured to execute the applications 362 based on the OS 361 or inresponse to signals received from eNBs or an operator. The processor 340is also coupled to the I/O interface 345, which provides the UE 116 withthe ability to connect to other devices, such as laptop computers andhandheld computers. The I/O interface 345 is the communication pathbetween these accessories and the processor 340.

The processor 340 is also coupled to the touchscreen 350 and the display355. The operator of the UE 116 can use the touchscreen 350 to enterdata into the UE 116. The display 355 may be a liquid crystal display,light emitting diode display, or other display capable of rendering textand/or at least limited graphics, such as from web sites.

The memory 360 is coupled to the processor 340. Part of the memory 360could include a random access memory (RAM), and another part of thememory 360 could include a Flash memory or other read-only memory (ROM).

Although FIG. 3 illustrates one example of UE 116, various changes maybe made to FIG. 3. For example, various components in FIG. 3 could becombined, further subdivided, or omitted and additional components couldbe added according to particular needs. As a particular example, theprocessor 340 could be divided into multiple processors, such as one ormore central processing units (CPUs) and one or more graphics processingunits (GPUs). Also, while FIG. 3 illustrates the UE 116 configured as amobile telephone or smartphone, UEs could be configured to operate asother types of mobile or stationary devices.

FIG. 4A is a high-level diagram of transmit path circuitry. For example,the transmit path circuitry may be used for an orthogonal frequencydivision multiple access (OFDMA) communication. FIG. 4B is a high-leveldiagram of receive path circuitry. For example, the receive pathcircuitry may be used for an orthogonal frequency division multipleaccess (OFDMA) communication. In FIGS. 4A and 4B, for downlinkcommunication, the transmit path circuitry may be implemented in a basestation (eNB) 102 or a relay station, and the receive path circuitry maybe implemented in a user equipment (e.g. user equipment 116 of FIG. 1).In other examples, for uplink communication, the receive path circuitry450 may be implemented in a base station (e.g. eNB 102 of FIG. 1) or arelay station, and the transmit path circuitry may be implemented in auser equipment (e.g. user equipment 116 of FIG. 1).

Transmit path circuitry comprises channel coding and modulation block405, serial-to-parallel (S-to-P) block 410, Size N Inverse Fast FourierTransform (IFFT) block 415, parallel-to-serial (P-to-S) block 420, addcyclic prefix block 425, and up-converter (UC) 430. Receive pathcircuitry 450 comprises down-converter (DC) 455, remove cyclic prefixblock 460, serial-to-parallel (S-to-P) block 465, Size N Fast FourierTransform (FFT) block 470, parallel-to-serial (P-to-S) block 475, andchannel decoding and demodulation block 480.

At least some of the components in FIGS. 4A 400 and 4B 450 may beimplemented in software, while other components may be implemented byconfigurable hardware or a mixture of software and configurablehardware. In particular, it is noted that the FFT blocks and the IFFTblocks described in this disclosure document may be implemented asconfigurable software algorithms, where the value of Size N may bemodified according to the implementation.

Furthermore, although this disclosure is directed to an embodiment thatimplements the Fast Fourier Transform and the Inverse Fast FourierTransform, this is by way of illustration only and may not be construedto limit the scope of the disclosure. It may be appreciated that in analternate embodiment of the present disclosure, the Fast FourierTransform functions and the Inverse Fast Fourier Transform functions mayeasily be replaced by discrete Fourier transform (DFT) functions andinverse discrete Fourier transform (IDFT) functions, respectively. Itmay be appreciated that for DFT and IDFT functions, the value of the Nvariable may be any integer number (i.e., 1, 4, 3, 4, etc.), while forFFT and IFFT functions, the value of the N variable may be any integernumber that is a power of two (i.e., 1, 2, 4, 8, 16, etc.).

In transmit path circuitry 400, channel coding and modulation block 405receives a set of information bits, applies coding (e.g., LDPC coding)and modulates (e.g., quadrature phase shift keying (QPSK) or quadratureamplitude modulation (QAM)) the input bits to produce a sequence offrequency-domain modulation symbols. Serial-to-parallel block 410converts (i.e., de-multiplexes) the serial modulated symbols to paralleldata to produce N parallel symbol streams where N is the IFFT/FFT sizeused in the BS 102 and the UE 116. Size N IFFT block 415 then performsan IFFT operation on the N parallel symbol streams to producetime-domain output signals. Parallel-to-serial block 420 converts (i.e.,multiplexes) the parallel time-domain output symbols from Size N IFFTblock 415 to produce a serial time-domain signal. Add cyclic prefixblock 425 then inserts a cyclic prefix to the time-domain signal.Finally, up-converter 430 modulates (i.e., up-converts) the output ofadd cyclic prefix block 425 to RF frequency for transmission via awireless channel. The signal may also be filtered at baseband beforeconversion to RF frequency.

The transmitted RF signal arrives at the UE 116 after passing throughthe wireless channel, and reverse operations to those at eNB 102 areperformed. Down-converter 455 down-converts the received signal tobaseband frequency, and remove cyclic prefix block 460 removes thecyclic prefix to produce the serial time-domain baseband signal.Serial-to-parallel block 465 converts the time-domain baseband signal toparallel time-domain signals. Size N FFT block 470 then performs an FFTalgorithm to produce N parallel frequency-domain signals.Parallel-to-serial block 475 converts the parallel frequency-domainsignals to a sequence of modulated data symbols. Channel decoding anddemodulation block 480 demodulates and then decodes the modulatedsymbols to recover the original input data stream.

Each of eNBs 101-103 may implement a transmit path that is analogous totransmitting in the downlink to user equipment 111-116 and may implementa receive path that is analogous to receiving in the uplink from userequipment 111-116. Similarly, each one of user equipment 111-116 mayimplement a transmit path corresponding to the architecture fortransmitting in the uplink to eNBs 101-103 and may implement a receivepath corresponding to the architecture for receiving in the downlinkfrom eNBs 101-103.

5G communication system use cases have been identified and described.Those use cases can be roughly categorized into three different groups.In one example, enhanced mobile broadband (eMBB) is determined to dowith high bits/sec requirement, with less stringent latency andreliability requirements. In another example, ultra reliable and lowlatency (URLL) is determined with less stringent bits/sec requirement.In yet another example, massive machine type communication (mMTC) isdetermined that a number of devices can be as many as 100,000 to 1million per km2, but the reliability/throughput/latency requirementcould be less stringent. This scenario may also involve power efficiencyrequirement as well, in that the battery consumption may be minimized aspossible.

FIG. 5 illustrates a network slicing 500 according to embodiments of thepresent disclosure. An embodiment of the network slicing 500 shown inFIG. 5 is for illustration only. One or more of the componentsillustrated in FIG. 5 can be implemented in specialized circuitryconfigured to perform the noted functions or one or more of thecomponents can be implemented by one or more processors executinginstructions to perform the noted functions. Other embodiments are usedwithout departing from the scope of the present disclosure.

As shown in FIG. 5, the network slicing 500 comprises an operator'snetwork 510, a plurality of RANS 520, a plurality of eNBs 530 a, 530 b,a plurality of small cell base stations 535 a, 535 b, a URLL slice 540a, a smart watch 545 a, a car 545 b, a, truck 545 c, a smart glasses 545d, a power 555 a, a temperature 555 b, an mMTC slice 550 a, an eMBBslice 560 a, a smart phone (e.g., cell phones) 565 a, a laptop 565 b,and a tablet 565 c (e.g., tablet PCs).

The operator's network 510 includes a number of radio access network(s)520—RAN(s)—that are associated with network devices, e.g., eNBs 530 aand 530 b, small cell base stations (femto/pico eNBs or Wi-Fi accesspoints) 535 a and 535 b, etc. The operator's network 510 can supportvarious services relying on the slice concept. In one example, fourslices, 540 a, 550 a, 550 b and 560 a, are supported by the network. TheURLL slice 540 a to serve UEs requiring URLL services, e.g., cars 545 b,trucks 545 c, smart watches 545 a, smart glasses 545 d, etc. Two mMTCslices 550 a and 550 b serve UEs requiring mMTC services such as powermeters and temperature control (e.g., 555 b), and one eMBB slice 560 arequiring eMBB serves such as cells phones 565 a, laptops 565 b, tablets565 c.

In short, network slicing is a scheme to cope with various differentqualities of services (QoS) in the network level. For supporting thesevarious QoS efficiently, slice-specific PHY optimization may also benecessary. Devices 545 a/b/c/d, 555 a/b are 565 a/b/c examples of userequipment (UE) of different types. The different types of user equipment(UE) shown in FIG. 5 are not necessarily associated with particulartypes of slices. For example, the cell phone 565 a, the laptop 565 b andthe tablet 565 c are associated with the eMBB slice 560 a, but this isjust for illustration and these devices can be associated with any typesof slices.

One device is configured with more than one slice. In one embodiment,the UE, (e.g., 565 a/b/c) is associated with two slices, the URLL slice540 a and the eMBB slice 560 a. This can be useful for supporting onlinegaming application, in which graphical information are transmittedthrough the eMBB slice 560 a, and user interaction related informationare exchanged through the URLL slice 540 a.

In the current LTE standard, no slice-level PHY is available, and mostof the PHY functions are utilized slice-agnostic. A UE is typicallyconfigured with a single set of PHY parameters (including transmit timeinterval (TTI) length, OFDM symbol length, subcarrier spacing, etc.),which is likely to prevent the network from (1) fast adapting todynamically changing QoS; and (2) supporting various QoS simultaneously.

It is noted that “slice” is a terminology introduced just forconvenience to refer to a logical entity that is associated with commonfeatures, for example, numerology, an upper-layer (including mediumaccess control/radio resource control (MAC/RRC)), and shared UL/DLtime-frequency resources. Alternative names for “slice” include virtualcells, hyper cells, cells, etc.

For mmWave bands, the number of antenna elements can be large for agiven form factor. However, the number of digitally chain to be limiteddue to hardware constraints (such as the feasibility to install a largenumber of ADCs/DACs at mmWave frequencies) as illustrated in FIG. 6. Inthis case, one digital chain is mapped onto a large number of antennaelements which can be controlled by a bank of analog phase shifters. Onedigital chain can then correspond to one sub-array which produces anarrow analog beam through analog beamforming. This analog beam can beconfigured to sweep across a wider range of angles by varying the phaseshifter bank across symbols or subframes.

FIG. 6 illustrates an example number of digital chains 600 according toembodiments of the present disclosure. An embodiment of the number ofdigital chains 600 shown in FIG. 6 is for illustration only. One or moreof the components illustrated in FIG. 6 can be implemented inspecialized circuitry configured to perform the noted functions or oneor more of the components can be implemented by one or more processorsexecuting instructions to perform the noted functions. Other embodimentsare used without departing from the scope of the present disclosure.

A gNB could utilize one or multiple transmit beams to cover the wholearea of one cell. The gNB may form a transmit beam by applying suitablegains and phase settings to an antenna array. The transmit gain, i.e.,the amplification of the power of the transmitted signal provided by atransmit beam, is typically inversely proportional to the width or areacovered by the beam. At lower carrier frequencies, the more benignpropagation losses may make it feasible for gNB to provide coverage witha single transmit beam, i.e., ensure adequate received signal quality atall UE locations within the coverage area via the usage of a singletransmit beam. In other words, at lower transmit signal carrierfrequencies, the transmit power amplification provided by the transmitbeam with a width large enough to cover the area may be sufficient toovercome the propagation losses to ensure adequate received signalquality at all UE locations within the coverage area.

However, at higher signal carrier frequencies, the transmit beam poweramplification corresponding to the same coverage area may not besufficient to overcome the higher propagation losses, resulting in adegradation of received signal quality at UE locations within thecoverage area. In order to overcome such a received signal qualitydegradation, the gNB may form a number of transmit beams, each providingcoverage over a region narrower than the overall coverage region, butproviding the transmit power amplification sufficient to overcome thehigher signal propagation loss due to the usage of higher transmitsignal carrier frequencies.

A few embodiments to transmit the minimum system informationtransmission in an advanced communication is considered in the presentdisclosure.

In some embodiments, remaining minimum system information is transmittedvia other channels at least partially indicated by NR-PBCH. In oneexample, the NR-PBCH carries a part of minimum system informationincluding information necessary for the UE to receive channel carryingremaining minimum system information. In another example, the NR-PBCHcarries information necessary for the UE to perform initial ULtransmission (not limited to NR-PRACH, e.g. PRACH msg. 1) and possiblyinformation necessary to receive the response to initial UL transmission(e.g., PRACH msg. 2) in addition to information in the aforementionedexample.

In some embodiments, remaining minimum system information is transmittedvia other channels not indicated in the NR-PBCH. In one example, theNR-PBCH carries information necessary for the UE to perform initial ULtransmission (not limited to NR-PRACH, e.g. PRACH msg. 1) andinformation necessary to receive the response to initial UL transmission(e.g. PRACH msg. 2). In such example, information necessary to receiveremaining minimum system information is provided after initial ULtransmission.

In some embodiments, the NR-PBCH carries all of minimum systeminformation.

In the LTE specifications, an MIB is periodically broadcast with 40 msecperiodicity, SIB-1 is periodically broadcast with 80 msec periodicity,and SIB-2 is also periodically broadcast, whose periodicity isconfigured by SIB-1.

The MIB uses a fixed schedule with a periodicity of 40 ms andrepetitions made within 40 ms. The first transmission of the MIB isscheduled in subframe #0 of radio frames for which the SFN mod 4=0, andrepetitions are scheduled in subframe #0 of all other radio frames. Fortime division duplex/frequency division duple (TDD/FDD) system with abandwidth larger than 1.4 MHz that supports BL UEs or UEs in CE, MIBtransmission may be repeated in subframe#9 of the previous radio framefor FDD and subframe #5 of the same radio frame for TDD.

FIG. 7 illustrates an example system information block transmission 700according to embodiments of the present disclosure. An embodiment of thesystem information block transmission 700 shown in FIG. 7 is forillustration only. One or more of the components illustrated in FIG. 7can be implemented in specialized circuitry configured to perform thenoted functions or one or more of the components can be implemented byone or more processors executing instructions to perform the notedfunctions. Other embodiments are used without departing from the scopeof the present disclosure.

The SystemInformationBlockType1 uses a fixed schedule with a periodicityof 80 ms and repetitions made within 80 ms. The first transmission ofSystemInformationBlockType1 is scheduled in subframe #5 of radio framesfor which the SFN mod 8=0, and repetitions are scheduled in subframe #5of all other radio frames for which SFN mod 2=0. The SIB1 transmissionopportunities according to legacy LTE are illustrated in FIG. 7. Theother SIBs can be transmitted in only those subframes which are notdestined for SIB1 transmissions.

The SI messages are transmitted within periodically occurring timedomain windows (referred to as SI-windows) using dynamic scheduling.Each SI message is associated with a SI-window and the SI-windows ofdifferent SI messages do not overlap. That is, within one SI-window onlythe corresponding SI is transmitted. The length of the SI-window iscommon for all SI messages, and is configurable. Within the SI-window,the corresponding SI message can be transmitted a number of times in anysubframe other than MBSFN subframes, uplink subframes in TDD, andsubframe #5 of radio frames for which SFN mod 2=0. The UE acquires thedetailed time-domain scheduling (and other information, e.g.frequency-domain scheduling, used transport format) from decoding asystem information radio network temporary identifier (SI-RNTI) onPDCCH.

For UEs other than BL UE or UEs in CE SI-RNTI is used to addressSystemInformationBlockType1 as well as all SI messages.SystemInformationBlockType1 configures the SI-window length and thetransmission periodicity for the SI messages.

In some embodiments, when acquiring an SI message, the UE may determinethe start of the SI-window for the concerned SI message as follows. Inone example, for the concerned SI message, the UE determines the numbern which corresponds to the order of entry in the list of SI messagesconfigured by schedulingInfoList in SystemInformationBlockType1. Inanother example, the UE determines the integer value x=(n−1)*w, where wis the si-WindowLength. In yet another example, the SI-window starts atthe subframe #a, where a=x mod 10, in the radio frame for which SFN modT=FLOOR(x/10), where T is the si-Periodicity of the concerned SImessage. In such instance, a network may configure an SI-window of 1 msonly if all SIs are scheduled before subframe #5 in radio frames forwhich SFN mod 2=0.

In some embodiments, the UE receives DL-SCH using the SI-RNTI from thestart of the SI-window and continue until the end of the SI-window whoseabsolute length in time is given by si-WindowLength, or until the SImessage was received, excluding the following subframes: a subframe #5in radio frames for which SFN mod 2=0; any MBSFN subframes; and/or anyuplink subframes in TDD. If the SI message was not received by the endof the SI-window, repeat reception at the next SI-window occasion forthe concerned SI message.

In the present disclosure, an SS burst set means a set of N₁ SS bursts;the SS burst set is periodically recurring with period P, where P is aninteger, e.g., 5, 10, 20, 40, 80, etc. in terms of millisecond and N₁ isan integer, e.g., 1, 2 or 4. An SS burst means a set of consecutive N₂SS blocks, where N₂ is an integer, e.g., 7, 14, 28, 56. An SS blockcomprises a combination of synchronization signals, broadcast signals,and reference signals, which are multiplexed in TDM, FDM, CDM or hybridmanner. A cell coverage is provided by a beam sweep over SS blockscomprising a burst set. Different TRP Tx beams may be used for differentSS blocks within a burst set.

FIG. 8 illustrates an example SS block transmission 800 according toembodiments of the present disclosure. An embodiment of the SS blocktransmission 800 shown in FIG. 8 is for illustration only. One or moreof the components illustrated in FIG. 8 can be implemented inspecialized circuitry configured to perform the noted functions or oneor more of the components can be implemented by one or more processorsexecuting instructions to perform the noted functions. Other embodimentsare used without departing from the scope of the present disclosure.

In some embodiments, the SS burst set consists of eight SS burst andeach SS burst consist of fourteen SS blocks, as illustrated in FIG. 8.One SS block consists of FDMed PSS, SSS, and ESS.

The present disclosure describes some schemes for transmitting remainingminimum system information (RMSI) and other SI in advanced wirelesssystems, in conjunction with multi-beam and single-beam operations.

The minimum SI can split into MIB (master information block) and RMSI(remaining minimum SI). The MIB is repeatedly transmitted on PBCH ineach P-msec window, and the PBCH transmission windows are recurringperiodically with periodicity P msec. The RMSI transmissionopportunities may be predefined or indicated by an information elementin MIB.

The RMSI transmission opportunities indicated in the MIB, denoted asRMSI resource configuration, may comprise one or more of the followingparameters and the information can be separately or jointly coded.

The RMSI resource configuration comprises an RMSI window which is usedto define an interval within which RMSI transmission may occur.

The RMSI resource configuration comprises a periodicity of RMSItransmissions (e.g., in terms of msec or in terms of number of radioframes), P_(RMSI), which may also correspond to the RMSI window size.The RMSI is repeatedly transmitted within each RMSI window, and the RMSIcontents are identical within the RMSI window. The RMSI window may alsobe referred to RMSI TTI.

The RMSI resource configuration comprises an RMSI time offset in termsof slots or msec, the time offset from the start of an RMSI window forthe first occurrence of RMSI transmission in the RMSI window. In oneexample, given an RMSI time offset x (units of msec), and P_(RMSI) isdefined in units of radio frames, the RMSI transmission may occur withinan RMSI window beginning at subframe x in a radio frame satisfying SFNmod P_(RMSI)=FLOOR (x/10)

The RMSI resource configuration comprises an RMSI burst size, i.e.,number of consecutive slots or mini-slots (or CORESETs (control resourcesets) and PDSCHs for RMSI) allocated for the RMSI transmission. Theburst size can be greater than one for supporting multi-beam sweepingoperation. When multi-beam sweeping may be performed either acrossmultiple blocks of consecutive OFDM symbols comprising the burst, onebeam per block, or across multiple mini-slots comprising the burst, onebeam per mini-slot. A UE may assume that a set of antenna ports used forPDSCH (and PDCCH) in each block/mini-slot are QCL'ed in Rx beam/mode(spatial parameters), and other large scale parameters such as delay andDoppler. The RMSI burst size may be equal to the number of actuallytransmitted SS blocks. In such a case, the RMSI burst size may beimplicitly indicated by the number of actually transmitted SS blocks; orthe number of actually transmitted SS blocks is implicitly indicated bythe RMSI burst size.

The RMSI transmission comprises RMSI block length (or RMSI mini-slotlength), i.e., the number of consecutive OFDM symbols (inreference/configured numerology) to comprise a mini-slot or a block. Inthis disclosure, “block” and “mini-slot” may mean the same and are usedinterchangeably. Note that an RMSI block may comprise time frequencyresources for a CORESET and the PDSCH for the RMSI.

The RMSI resource configuration comprises RMSI block bandwidth (or RMSImini-slot bandwidth), i.e., the bandwidth allocated for the mini-slotsor blocks to be used for the RMSI transmissions.

The RMSI resource configuration comprises an RMSI duty cycle within eachRMSI window (e.g., the time interval between two adjacent RMSItransmissions within an RMSI window. This field is valid only when thenumber of RMSI bursts in an RMSI window is greater than one.

The RMSI resource configuration comprises an RMSI-PDCCH indicator: onebit information to indicate the UE whether to search for PDCCH forreceiving the RMSI transmissions or not. When the UE is indicated tosearch for PDCCH, the RMSI is transmitted on a PDSCH scheduled by thePDCCH, wherein the MCS and the PDSCH bandwidth (BW) are indicated by thePDCCH per slot (or per mini-slot or per block). When the UE is indicatednot to search for PDCCH for RMSI reception, the RMSI is transmitted on apre-defined BW and with a pre-defined MCS. For example, the pre-definedBW is the same as the system BW.

The RMSI resource configuration comprises MCS, PRB allocations; the MCSand PRBs to receive the PDSCH conveying the RMSI.

Some of those parameters, in the aforementioned examples, not explicitlyconfigured by RMSI resource configuration can be pre-configured orindicated by PDCCH in each slot/mini-slot in RMSI burst. In such case, afirst subset of those parameters listed above is pre-configured; asecond subset is configured in MIB, and a third subset is indicated inthe PDCCH; and the first and the second and the third subsets aremutually exclusive and the union of them is equal to the set ofparameters.

FIG. 9 illustrates an example RMSI transmission 900 according toembodiments of the present disclosure. An embodiment of the RMSItransmission 900 shown in FIG. 9 is for illustration only. One or moreof the components illustrated in FIG. 9 can be implemented inspecialized circuitry configured to perform the noted functions or oneor more of the components can be implemented by one or more processorsexecuting instructions to perform the noted functions. Other embodimentsare used without departing from the scope of the present disclosure.

The bit-width and contents of the RMSI resource configuration can bedifferent for the different sets of carrier frequencies. A first setcorresponds to carrier frequency ranges >6 GHz, e.g., 15 GHz, 28 GHz, 30GHz, 60 GHz, etc., and the second set corresponds to carrier frequencyranges <6 GHz, e.g., 2, 3.5 and 4 GHz.

In some embodiments, if the carrier frequency belongs to the first set,the UE may assume the pre-configured RMSI reception resources; and ifthe carrier frequency belongs to the second set, the UE may decode PDCCHto get indication of the PDSCH BW and MCS for the RMSI.

In some embodiments, if the carrier frequency belongs to the first set,the UE may assume that x>0 bits are allocated to the RMSI resourceconfiguration; else if the carrier frequency belongs to the second set,the UE may assume that 0 bits are allocated to the configuration. Forthe second case, the RMSI transmission occasions are pre-configured, andnon-adaptable.

In some embodiments, if the carrier frequency belongs to the first set,the bit width for RMSI burst size is y>0 bits to indicate one number outof multiple candidates; if the carrier frequency belongs to the secondset, the bit width is zero, in which case the RMSI burst size is equalto a pre-configured value, e.g., 1 time slot.

The scheduling information payload transmitted on NR-PBCH can bedifferent for single-beam (the second set of carrier frequency) andmulti-beam sweeping case (the first set). In both cases, some schedulinginformation may be pre-configured. For multi-beam sweeping case (thefirst set), PBCH indicates necessary PDSCH scheduling information forRMSI. For single-beam case (the second set), PBCH and PDCCH jointlyindicate necessary PDSCH scheduling information for RMSI.

The RMSI can be transmitted on SS beam specifically, and the UE isconfigured to assume that the number of blocks or mini-slots allocatedin each RMSI burst are identical to the number of SS blocks in a SSburst (or a SS burst set). The number of SS blocks can bepre-configured, or indicated in the MIB. In such a case, when the UE hasdetected SS/PBCH in SS block ID #n, the UE can attempt to decode theRMSI on the n-th RMSI block, and skip decoding the other RMSI blocks tosave UE power consumption. For the n-th SS block and the n-th RMSIblock, the UE may assume that those antenna ports in these two types ofblocks are coherent, and QCL'ed in the large scale parameters, includingRx mode (spatial parameters), delay and Doppler spreads/parameters. Onthe other hand, for differently numbered SS block and RMSI block, a UEmay not assume that those antenna ports are coherent; and UE may notassume that those antenna ports are QCL'ed.

Alternatively, the number of RMSI blocks in each RMSI burst can beconfigured to be less than the number of beams (or blocks) configuredfor an SS burst set. In such case, the UE may try to decode the RMSIacross all the configured RMSI blocks in each RMSI burst. When thenumber of UEs is small, this scheme can be more efficient in terms ofnetwork power consumption and consume less system overhead. In thiscase, a UE may not assume that those antenna ports in RMSI blocks and SSblocks are coherent; and a UE may not assume that those antenna ports inthese different blocks are QCL'ed.

The SIB-PDCCH/PDSCH (denoted as S-PxCH later in this disclosure)transmission opportunity can be configured utilizing similar set ofparameters as the RMSI as shown in the aforementioned embodiments, butthose parameters are indicated in RMSI rather than in MIB, and thecontents are for SIB-PDSCH rather than for RMSI.

The S-PxCH can be transmitted on RMSI beam specifically, and the UE isconfigured to assume that a number of blocks or mini-slots allocated ineach S-PxCH burst are identical to the number of RMSI blocks in an RMSIburst. In such a case, when a UE has detected RMSI in RMSI block #n, theUE can attempt to decode the S-PxCH on the n-th S-PxCH block, and skipdecoding the other blocks to save UE power consumption. For the n-thRMSI block and the n-th S-PxCH block, the UE may assume that thoseantenna ports in these two types of blocks are coherent, andquasi-co-located (QCL'ed) in the large scale parameters, including Rxmode (spatial parameters), delay and Doppler spreads/parameters. On theother hand, for differently numbered RMSI block and S-PxCH block, the UEmay not assume that those antenna ports are coherent; and the UE may notassume that those antenna ports in those different blocks are QCL'ed.

Alternatively, the number of S-PxCH blocks in each S-PxCH burst can beconfigured to be less than (in general, different from) the number ofbeams (or blocks) configured for an RMSI burst set. In such a case, theUE may try to decode the S-PxCH across all the configured S-PxCH blocksin each S-PxCH burst. When the number of UEs is small, this scheme canbe more efficient in terms of network power consumption and consume lesssystem overhead. In this case, the UE may not assume that those antennaports in S-PxCH blocks and RMSI blocks are coherent; and the UE may notassume that those antenna ports are QCL'ed.

The numbers of RMSI/S-PxCH blocks in all the RMSI/S-PxCH bursts withinan RMSI/S-PxCH window are identical. For the same RMSI/S-PxCH blockposition across different RMSI bursts (e.g., RMSI/S-PxCH block n acrossall the RMSI/S-PxCH bursts) within a RMSI/S-PxCH window, a UE may assumethat TRP has applied the same beam. In such a case, the UE may assumethat those antenna ports in these blocks are coherent, and QCL'ed in thelarge scale parameters, including Rx mode (spatial parameters), delayand Doppler spreads/parameters.

On the other hand, for differently numbered RMSI/S-PxCH blocks withinand across RMSI/S-PxCH window(s), the UE may not assume that thoseantenna ports are coherent; and the UE may not assume that those antennaports are QCL'ed.

For RMSI and/or SIB and/or paging transmission, a set of PDCCH searchspaces (i.e., CORESETs) can be configured. The numerology used for thePDCCH transmissions is determined as a function of the defaultnumerology. In case of up to 120 kHz numerology, PDSCH can be reliablytransmitted; however, in case of 240 kHz numerology, PDSCH may not beable to be reliably transmitted. Hence, it is proposed to use thefollowing mapping as shown in TABLE 1 between the default numerology andCORESET numerology for the RMSI/SIB. In the below table, frequency bandA, B are defined in sub 6 GHz range; and C, D are defined in over 6 GHzrange.

TABLE 1 Mapping information Frequency Default subcarrier spacingSubcarrier spacing for the band for SS blocks (kHz) common search spaceA 15 15 B 30 30 C 120 120 D 240 120

For enhancing the SS block coverage, a same beam can be used acrossmultiple SS blocks. A UE default assumption is such that the beams usedfor different blocks are different. However, the UE can be indicated (ina broadcast signaling, e.g., in MIB) such that the UE can assume that SSblocks belonging to a group are transmitted using a same beam. In such acase, the UE can derive a SS block RSRP with averaging the measurementsmeasured across the multiple SS blocks belonging to a same group.

For the QCL association between the SS blocks and CORESETs, eitherone-to-one mapping or many-to-one mapping can be used. The mappingrelationship (i.e., either one-to-one or many-to-one) and/or relatedparameters (e.g., J_(max) and/or N_(G) whose definitions are asexplained below) can be configured in a broadcast signaling, e.g., MIB.

When many-to-one mapping is configured, SS block group j is QCLed withRMSI block j, where=0, . . . , J_(max)−1, where J_(max) is the totalnumber of configured CORESETs (this corresponds to the number of SSblock groups). In this case, the total number of (actually transmitted)SS blocks is equal to N_(G)·J_(max), where N_(G) is number of SS blocksper SS block group.

The SS block indices belonging to group j is {(j−1)·N_(G)+0, 1, . . . ,N_(G)−1}. When many-to-one mapping is configured, the UE can derive theSS block RSRP per SS block group. For the inter-cell measurement in theCONNECTED mode, the mapping relationship (i.e., either one-to-one ormany-to-one) and/or related parameters (e.g., J_(max) and/or N_(G)) canbe configured in a dedicated signaling related to SS block based RSRPmeasurement.

When one-to-one mapping is configured, SS block j is QCLed with RMSIblock (CORESET) j in a set of QCL parameters, where j=0, . . . ,J_(max)−1, where J_(max) is the total number of (actually transmitted)SS blocks. In this case, N_(G)=1. The length of the RMSI block can bejointly determined/indicated with the number of SS blocks per SS blockgroup, i.e., N_(G).

If the UE is indicated/configured to search for RMSI PDCCH, the cyclicredundancy check (CRC) which is associated with the scheduling downlinkcontrol information (DCI) may be scrambled with a specific RMSI-RNTI.

In some embodiments, if each RMSI block utilizes a different tx beam, abeam specific RMSI-RNTI is applied to the CRC generated for that DCIduring NR-PDCCH scheduling that RMSI block. This is done so by settingthe low order 6 bits of the RMSI_RNTI to equal the SS Block Time Index(0-6 bits) signaled in the MIB. This also requires that the tx beam usedfor the RMTI block is the same as the same tx beam used for the SS blockcorresponding to that time index. A UE tries to decode each RMTI blockapplying the corresponding SS block beam and the corresponding beamspecific RMSI RNTI.

In another some embodiments, the CRC for the RMSI payload of RMSI Block#n is scrambled with the SS block time index for the associated SSBlock, e.g., in terms of spatial QCL assumptions.

The RMSI CORESET(s) may be configured per SS burst set, or per SS burst,or per SS block.

If the RMSI CORESET(s) are configured per SS burst set, the RMSIscheduling information in the MIB is identical in the SS blockscomprising an SS burst set. In one embodiment, the RMSI schedulinginformation is determined by an offset delayed by the time resource ofthe SS block and the offset number is indicated within the MIB. Inanother embodiment, the RMSI scheduling information is indicated by anoffset, in units of either radio frames or half radio frames, relativeto the radio frame number of the SS burst set.

If the RMSI CORESET(s) are configured per SS burst, the RMSI schedulinginformation in the MIB is identical in the SS blocks comprising an SSburst; but the information can be different across the MIBs transmittedin different SS bursts comprising an SS burst set.

If the RMSI CORESET(s) are configured per SS block, the RMSI schedulinginformation in the MIB can be different in different SS blockscomprising an SS burst set. In one embodiment, a single RMSI CORESET isindicated in the MIB conveyed by an SS block. The time-frequencyresource of the RMSI CORESET is determined solely by the MIB conveyed bythe SS block. In such case, the time resource of the RMSI CORESET isoffset delayed by the time resource of the SS block, and the offsetnumber is indicated in the respective (beam-specific) MIB. The offsetvalue can be indicated in terms of number of OFDM symbols, number ofslots in the frame structure defined by the default (SS block)numerology, or alternatively by the configured RMSI numerology.

The beam-specific alternative may allow more efficient CORESETconfiguration, as only a single CORESET needs to be configured byindividual SS-block specific MIB. Still, most of the CORESETconfiguration information is likely to be common across all theSS-blocks; but some information may be SS-block specific, e.g., theCORESET timing configuration. When compared to the other alternative inwhich the timing of all the CORESETs are configured in a batch, it canbe seen that this alternative requires smaller MIB payload because onlya single timing needs to be configured. This may also imply that themany-to-one mapping from SS-blocks to CORESETs to make QCL relations arehandled by the network implementations, and no bits need to be spent formaking the QCL relation. It may need to clarify that the configuredCORESET by an SS block is QCL'ed with QCL parameters including thespatial parameters.

In some embodiments, a CORESET configuration in MIB in an SS blockindicates a single CORESET in which PDCCH DMRS is QCL'ed with the SSblock at least in spatial parameters. In such embodiment, different SSblocks may indicate different CORESETs.

In one embodiment, N candidate parameter value sets for CORESET mappingare hard coded in a table, and log 2(N) bit information to be carried inMIB indicates which one to be used. Each parameter value set comprises asubset of parameters discussed in embodiment 1, i.e., selected fromCORESET periodicity, a CORESET time offset (either wrt a first SS block,or wrt a frame boundary), a CORESET burst size, a CORESET length (i.e.,in terms of OFDM symbols), CORESET or RMSI/SIB BW super set (oralternatively denoted as PDSCH super set BW that may be assumed for thescheduling assignment in the PDCCH scheduling the PDSCH for SIB/RMSI)and CORESET duty cycle. The rest of the parameters that are notspecified in the table either have a constant value; or configuredexplicitly using other field in the MIB.

In another embodiment, the CORESET BW, the PDSCH super set BW, andCORESET time locations are either jointly or separately indicated in theMIB.

The CORESET BW may be configured explicitly in the MIB (e.g., one BWselected from multiple candidate BWs within a carrier-specific minimumBW, i.e., minCH BW as shown in TABLE 2); or alternatively, the CORESETBW is configured/hard-coded to be the same as the SS block BW or theminimum BW of the carrier frequency. The motivation of the alternativeCORESET BW allocation is to support both types of UEs, i.e., narrow-BWUEs and wide-BW UEs.

TABLE 2 Multiple candidate BWs Frequency SCS Min CHBW Max CHBW range(kHz) (MHz) (MHz) Range 1 15  5 50 Range 1 30 Option 1: 5 MHz 100 Option2: 10 MHz Range 1 60 Option 1: 10 MHz 100 MHz Option 2: 20 MHz Range 260 50 200 Range 2 120 50 400 MHz

A PDSCH super set BW can be configured to be wider than or equal to theCORESET BW. The RA field in the PDCCH configured in the CORESET isdefined according to the PDSCH superset BW. Several alternatives toconfigure the PDSCH super set BW can be considered.

In some embodiments, the PDSCH super set BW is hard coded to be the sameas CORESET BW.

In some embodiments, the PDSCH super set BW is indicated in the MIB.

In one such example, the indicated BW value is selected from (1) CORESETBW or the minimum BW in the frequency band (i.e., minCH BW); and (2) aminimum BW that narrow-BW UE supports in the frequency band. The minimumBW in (2) value may be specified by means of the minimum supported UEcapability.

In the LTE specification, the minimum supported UE BW receptioncapability is 20 MHz; in NR the minimum supported UE BW receptioncapability can be more than the minimum BW of (1). This example isuseful when the BW to be supported by minimum capability UE is widerthan the CORESET BW in the frequency band, and when the bandwidth partsupported by the network has wider than or equal to the minimum BW.

In another example, the indicated BW value is selected from (1) CORESETBW or the minimum BW in the frequency band; (2) a first BW; (3) a secondBW; (4) a third BW. These examples give more flexibility to the networkon how to configure the CORESET BW.

In yet another example, the indicated BW value is selected from (1) SSblock BW; (2) 1× BW-part BW; (3) 2× BW-part BW; and/or (4) 4× BW-partBW.

The configuration of the BW of a BW part can be conducted in variousschemes. In one alternative, the BW of a BW part is specified/hard-codedper carrier frequency band. In another alternative, the BW of a BW partis explicitly configured/indicated in MIB (or SIBx). In yet anotheralternative, each BW part is defined in terms of a subset of resourceblock groups (RBGs), when the system BW is partitioned into a set ofRBGs, for which the RBGs are numbered according to a numbering scheme,wherein the RBG size for this purpose may be hard coded to be a constantinteger, e.g., 1, 2, 3 RBs.

The BW of the BW part can be defined in terms of the number of RBGs. Thecandidate number of RBGs may be hard-coded and the UE may be indicatedwith one value in the MIB to determine the BW of the BW part. In theinitial-access stage when the UE just obtain MIB, the UE does not knowthe system BW but the UE only knows the minimum BW (or SS block BW)around the decoded PBCH (or detected SS blocks). In such a case, the RBGindexing cannot be across the whole system BW.

FIG. 10 illustrates an example RBG transmission 1000 according toembodiments of the present disclosure. An embodiment of the RBGtransmission 1000 shown in FIG. 10 is for illustration only. One or moreof the components illustrated in FIG. 10 can be implemented inspecialized circuitry configured to perform the noted functions or oneor more of the components can be implemented by one or more processorsexecuting instructions to perform the noted functions. Other embodimentsare used without departing from the scope of the present disclosure.

In one example, an SS block BW center is numbered as RBG x; and othersurrounding RBGs are indexed sequentially, with assigning integer valuesincreased from x towards one (“plus”) direction of frequency (i.e., x+1,x+2, . . . ); and with assigning integer values decreased from x towardsthe other (“minus”) direction of frequency (i.e., x−1, x−2, . . . ) asshown in FIG. 10. In FIG. 10, the integer value x may be hard coded orindicated in the MIB.

The center frequency location of the BW part may be separately indicatedin terms of the frequency offset (e.g., in terms of number of frequencyresource units (e.g., RBGs number of subcarriers, RBs, etc.) towardseither positive or negative directions) to the center frequency of theSS block. In one example, a UE may be indicated with an integer value yin the MIB, which can be either negative, positive or zero, so that theUE can identify the center RBG of the BW part to receive RMSI isdetermined to be x+y. The candidate values of y that can be indicated inthe MIB may be hard coded per carrier frequency band.

Time domain CORESET location within a slot can be indicated in the MIB.The indicated information may include CORESET composition in each slotcontaining CORESET(s).

In one alternative, X candidate CORESET time locations in each slot toconvey CORESETs (defined by SS block numerology or alternativelyconfigured/indicated RMSI numerology) may be specified. Each candidatetime location may be specified in terms of a set of OFDM symbol numbers;or alternatively in terms of the starting OFDM symbol number and theending OFDM symbol number; or alternatively in terms of the startingOFDM symbol number and the number of OFDM symbols.

A UE may be indicated in MIB one selected from the X candidate CORESETtime locations. One example CORESET time locations with X=4 isconstructed in TABLE 3. According to TABLE 3, when the candidate number0 is indicated a CORESET comprises one OFDM symbol, i.e., OFDM symbol 0;when the candidate number 1 is indicated, a CORESET comprises two OFDMsymbols, i.e., OFDM symbol 0 and 1; and so on. The total number of slotsto map CORESETs is implicitly determined by the number of CORESETs (orthe number of SS blocks) indicated in the MIB; in one example, the totalnumber of slots is the same as the number of CORESETs (or the number ofSS blocks).

Note that the indicated number of the field in MIB is just for theillustration. In TABLE 3, a subset of entries, or the subset withdifferent indices can be constructed without departing from theprinciple of the present disclosure.

TABLE 3 CORESET time location Indicated An indicated (Starting symbol(starting symbol number set of OFDM number, number, of the symbol numberof ending symbol field in MIB numbers symbols) number) 0 0 (0, 1) (0, 0)1 0, 1 (0, 2) (0, 1) 2 0, 1, 2 (0, 3) (0, 2) 3 0, 1, 2, 3 (0, 4) (0, 3)4 1 (1, 1) (1, 1) 5 2, 3 (2, 2) (2, 3)

In some embodiments, both time slot offset (k) and OFDM symbol numbersare indicated in the beam-specific CORESET configuration in MIB. Thetime slot offset (k) may be indicated with respect to the time slot (n)of the detected SS block; or alternative, with respect to the frameboundary. The CORESET is located in the specified OFDM symbols in timeslot n+k.

In some embodiments, a UE is indicated in MIB of (1) the number ofCORESETs in each slot, N_(CS); (2) the number of OFDM symbols perCORESET, L₂ and (3) the corresponding CORESET locations in the slot. Inthis case, the total number of slots to map the CORESETs N_(S), isdetermined by the total number of CORESETs N_(C), and the number ofCORESETs in each slot, N_(CS): in one method N_(S)=N_(C)/N_(CS).

In some embodiments, the starting symbols of the CORESETs are determinedas a function of (1) the number of CORESETs in each slot, N_(CS); and(2) the number of OFDM symbols per CORESET, L₂. The candidate numbersfor NCS are 1, 2, 4. The candidate numbers for L2 are 1, 2, and 3. Thesetwo numbers (1) and (2) may be jointly or separately indicated in theMIB. Alternatively, one of these two numbers is explicitly indicatedwhile the other number is hard coded in the spec. In one example, one ofthese two numbers is explicitly indicated while the other number isimplicitly indicated. For example, the number of CORESETs in each slotis implicitly determined as a function of number of SS bursts. In suchcase, the number of CORESETs in each slot is the same as the number ofSS bursts. In such case, a UE identifies the number of CORESETs in eachslot utilizing a mapping table between the number of CORESETs in eachslot and the number of SS bursts.

FIG. 11 illustrates an example CORESET transmission 1100 in continuousand distributed mapping according to embodiments of the presentdisclosure. An embodiment of the CORESET transmission 1100 shown in FIG.11 is for illustration only. One or more of the components illustratedin FIG. 11 can be implemented in specialized circuitry configured toperform the noted functions or one or more of the components can beimplemented by one or more processors executing instructions to performthe noted functions. Other embodiments are used without departing fromthe scope of the present disclosure.

The CORESETs in a slot can be mapped in either distributed or contiguousmanner. When the N_(CS) CORESETs are distributed across symbols in aslot, the starting symbol of the CORESET i is determined as (i−1)*L₁where i=0, 1, . . . , N_(CS)−1 and L₁ is an integer that specifies thesymbol spacing between the two consecutive CORESETs. In one example,L₁=L/N_(CS) where L is the number of symbols in a slot. For example,when L=14 and N_(CS)=2, L₁=7. When the N_(CS) CORESETs are contiguousacross symbols in a slot, the starting symbol of the CORESET i isdetermined as (i−1)*L₂, where i=0, 1, . . . , N_(CS)−1. A UE may getindicated in MIB whether to use distributed or consecutive CORESETmapping for receiving the PDCCHs. These two CORESET mapping methods areillustrated in FIG. 11.

According to the aforementioned embodiments, the N_(CS) CORESETs aremapped each slot. There could be various methods to determine theidentities of the CORESETs to be mapped to the s-th slot used for theCORESET mapping for the common search space (this can be the same as anRMSI burst or an RMSI burst set), where s=1, 2, . . . , N_(S). In oneexample, on the s-th slot, CORESETs {(s−1)*N_(CS), . . . , s*N_(CS)−1}are sequentially mapped in the time domain. In another method, i-thCORESET in the s-th slot corresponds to an s-th CORESET in SS burst i.

The slots to be used for the CORESET can be every Z slots, or everyframe, etc., wherein Z=1, 2, . . . . One selected CORESET mapping schemeout of some of these candidate scheme can be indicated in MIB. For thispurpose, the number Z may be indicated in MIB. Some of these parametersto indicate for the time domain configuration of CORESETs may beindicated in MIB: number of CORESETs per slot (N_(CS)); number of OFDMsymbols per CORESET (L₂); distributed vs. contiguous mapping of CORESETsin a slot; and CORESET slot duty cycle (Z)

In some embodiments, the frequency domain mapping of MIB configuredCORESETs and RMSI PDSCH, numerology of RMSI, and multiplexing scheme ofCORESET/PDSCH and SS blocks are determined.

In some embodiments, for frequency location of CORESET for RMSIscheduling and NR-PDSCH for RMSI, CORESET for RMSI scheduling andNR-PDSCH for RMSI may not be confined within the same BW ofcorresponding NR-PBCH and bandwidth for CORESET and NR-PDSCH for RMSI isconfined within the UE minimum bandwidth for the given frequency band.In some embodiments, the single DL numerology to be used at least forRMSI, Msg.2/4 for initial access and broadcasted OSI is informed inNR-PBCH payload. In such embodiments, a numerology is used for paging,Msg.2/4 for other purposes, and on-demand OSI. In some embodiments, itis determined whether NR supports FDM between SS/PBCH block andCORESET/NR-PDSCH. In some embodiments, CORESET is designed at least forTDM.

To minimize fragmentation of the resources, it would be desirable toconfine these signals to be transmitted with the MIB configurednumerology, i.e., MIB configured CORESET, RMSI, RMSI configured CORESET,msg2/4 for initial access, broadcast OSI, etc. in a localizedtime-frequency resource. In particular, for the frequency domain, the BWto transmit these signals could comprise a single BW whose BW size isless than the UE minimum BW. Now the remaining issue is whether toadditionally support configuration of the single BW separately from theUE minimum BW which encompassing the SS block BW.

It seems that the FDM can be supported by configure the frequencylocation for the single BW in terms of frequency offset to the SS blockBW. If the candidate frequency offset values to be indicated in the MIBincludes “0” and other values corresponding to BWPs non-overlapping withthe SS block BW, then both TDM and FDM of the SS block and the single BWmay naturally be supported.

A single BW is configured in MIB by means of a frequency offset. Thesingle BW is to transmit these signals according to the MIB configurednumerology, i.e., MIB configured CORESET, RMSI, RMSI configured CORESET,msg2/4 for initial access, broadcast OSI, etc. This single BW can beaccessed in both IDLE and CONNECTED mode, to receive these signals. Inone example, the candidate values to indicate the frequency offsetinclude at least “0,” and other values that corresponds to BWPsnon-overlapping with the SS block BW. In another example, the number ofbits for the frequency offset is limited to 2 bits.

FIG. 12 illustrates a flow chart of a method 1200 for system informationdelivery, as may be performed by a UE, according to embodiments of thepresent disclosure. An embodiment of the method 1200 shown in FIG. 12 isfor illustration only. One or more of the components illustrated in FIG.12 can be implemented in specialized circuitry configured to perform thenoted functions or one or more of the components can be implemented byone or more processors executing instructions to perform the notedfunctions. Other embodiments are used without departing from the scopeof the present disclosure.

As shown in FIG. 12, the method 1200 begins at step 1205. In step 1205,the UE receives, from a BS, a SS/PBCH block comprising a PBCH thatcarries a MIB including an SIB1 CORESET configuration. In step 1205, theSIB1 CORESET configuration comprises a frequency location, a number ofRBs comprising an SIB1 CORESET associated with the SS/PBCH block, andinformation of time domain resources of the SIB1 CORESET. In someembodiments, the information of time domain resources of the SIB1CORESET includes a number of consecutive symbols for the SIB1 CORESET.In some embodiments, the SIB1 CORESET configuration further comprisesinformation to indicate a number of SIB1 CORESETs in each slot, acandidate value of the number of SIB 1 CORESETs is determined as either1 or 2. In some embodiments, the SIB1 CORESET configuration furthercomprises information to indicate a starting OFDM symbol number of theSIB1 CORESET.

Subsequently, the UE in step 1210 determines an initial active BWPcomprising the frequency location, the number of RBs comprising the SIB1CORESET, and a numerology of RMSI. In some embodiments, the frequencylocation of the SIB1 CORESET is configured by a frequency offset of theSIB1 CORESET bandwidth from the frequency location of the SS/PBCH block,the frequency offset being indicated in the MIB.

Finally, the UE in step 1215 receives a PDCCH mapped to at least onetime-frequency resource within the SIB1 CORESET. In step 1215, the PDCCHincludes scheduling information of a PDSCH containing an SIB 1. In someembodiments, the PDSCH delivering the SIB1 is confined within theinitial active BWP. In some embodiments, the UE in step 1215 uses a Rxbeam to receive the SIB1 CORESET based on a reception scheme of theSS/PBCH block.

Although the present disclosure has been described with an exemplaryembodiment, various changes and modifications may be suggested to oneskilled in the art. It is intended that the present disclosure encompasssuch changes and modifications as fall within the scope of the appendedclaims.

None of the description in this application should be read as implyingthat any particular element, step, or function is an essential elementthat must be included in the claims scope. The scope of patented subjectmatter is defined only by the claims. Moreover, none of the claims areintended to invoke 35 U.S.C. § 112(f) unless the exact words “means for”are followed by a participle.

What is claimed is:
 1. A user equipment (UE) for system informationtransmission in a wireless communication system, the UE comprising: atransceiver configured to receive, from a base station (BS), asynchronization signal/physical broadcasting channel (SS/PBCH) blockthat carries a master information block (MIB) including a configurationof a control resource set (CORESET) for a type 1 system informationblock (SIB1), wherein the SIB1 CORESET configuration comprises afrequency location, a number of resource blocks (RBs), and informationof time domain resources of the SIB1 CORESET; and a processor configuredto determine an initial active bandwidth part (BWP) comprising thefrequency location, the number of RBs comprising the SIB1 CORESET, and anumerology of remaining minimum system information (RMSI), wherein thetransceiver is further configured to receive, from the BS, a physicaldownlink control channel (PDCCH) mapped to at least one time-frequencyresource within the SIB1 CORESET, the PDCCH including schedulinginformation of a physical downlink shared channel (PDSCH) containing theSIB1.
 2. The UE of claim 1, wherein the frequency location of the SIB1CORESET is configured by a frequency offset from a frequency location ofthe SS/PBCH block, the frequency offset being indicated in the MIB. 3.The UE of claim 1, wherein the PDSCH containing the SIB1 is confinedwithin the initial active BWP.
 4. The UE of claim 1, wherein theinformation of time domain resources of the SIB1 CORESET includes anumber of consecutive symbols for the SIB1 CORESET.
 5. The UE of claim1, wherein the SIB1 CORESET configuration further comprises informationto indicate a number of SIB1 CORESETs in each slot, and wherein acandidate value of the number of SIB1 CORESETs is either 1 or
 2. 6. TheUE of claim 1, wherein the SIB1 CORESET configuration further comprisesinformation to indicate a number for a starting orthogonal frequencydivision multiplexing (OFDM) symbol of the SIB1 CORESET.
 7. The UE ofclaim 1, wherein the processor is further configured to use a receive(Rx) beam to receive the SIB1 CORESET based on a reception scheme of theSS/PBCH block.
 8. A base station (BS) for system informationtransmission in a wireless communication system, the BS comprising: aprocessor configured to determine an initial active bandwidth part (BWP)comprising a frequency location, a number of resource blocks (RBs)comprising a control resource set (CORESET) for a type 1 systeminformation block (SIB1), and a numerology of remaining minimum systeminformation (RMSI); and a transceiver configured to: transmit, to a userequipment (UE), a synchronization signal/physical broadcasting channel(SS/PBCH) block that carries a master information block (MIB) includinga configuration of the SIB1 CORESET, wherein the SIB1 CORESETconfiguration comprises a frequency location, a number of RBs, andinformation of time domain resources of the SIB1 CORESET, and transmit aphysical downlink control channel (PDCCH) mapped to at least onetime-frequency resource within the SIB1 CORESET, wherein the PDCCHincludes scheduling information of a physical downlink shared channel(PDSCH) containing the SIB1.
 9. The BS of claim 8, wherein the frequencylocation of the SIB1 CORESET is configured by a frequency offset from afrequency location of the SS/PBCH block, the frequency offset beingindicated in the MIB.
 10. The BS of claim 8, wherein the PDSCHcontaining the SIB1 is confined within the initial active BWP.
 11. TheBS of claim 8, wherein the information of time domain resources of theSIB1 CORESET includes a number of consecutive symbols for the SIB1CORESET.
 12. The BS of claim 8, wherein the SIB1 CORESET configurationfurther comprises information to indicate a number of SIB1 CORESETs ineach slot, and wherein a candidate value of the number of SIB1 CORESETsis either 1 or
 2. 13. The BS of claim 8, wherein the SIB1 CORESETconfiguration further comprises information to indicate a number of astarting orthogonal frequency division multiplexing (OFDM) symbol of theSIB1 CORESET.
 14. A method of user equipment (UE) for system informationtransmission in a wireless communication system, the method comprising:receiving, from a base station (BS), a synchronization signal/physicalbroadcasting channel (SS/PBCH) block that carries a master informationblock (MIB) including a configuration of a control resource set(CORESET) for a type 1 system information block (SIB1), wherein the SIB1CORESET configuration comprises a frequency location, a number ofresource blocks (RBs), and information of time domain resources of theSIB1 CORESET; determining an initial active bandwidth part (BWP)comprising the frequency location, the number of RBs comprising the SIB1CORESET, and a numerology of remaining minimum system information(RMSI); and receiving, from the BS, a physical downlink control channel(PDCCH) mapped to at least one time-frequency resource within the SIB1CORESET, wherein the PDCCH includes scheduling information of a physicaldownlink shared channel (PDSCH) containing the SIB1.
 15. The method ofclaim 14, wherein the frequency location of the SIB1 CORESET isconfigured by a frequency offset from a frequency location of theSS/PBCH block, the frequency offset being indicated in the MIB.
 16. Themethod of claim 14, wherein the PDSCH containing the SIB1 is confinedwithin the initial active BWP.
 17. The method of claim 14, wherein theinformation of time domain resources of the SIB1 CORESET includes anumber of consecutive symbols for the SIB1 CORESET.
 18. The method ofclaim 14, wherein the SIB1 CORESET configuration further comprisesinformation to indicate a number of SIB1 CORESETs in each slot, andwherein a candidate value of the number of SIB1 CORESETs is either 1 or2.
 19. The method of claim 14, wherein the SIB1 CORESET configurationfurther comprises information to indicate a number of a startingorthogonal frequency division multiplexing (OFDM) symbol of the SIB1CORESET.
 20. The method of claim 14, further comprising using a receive(Rx) beam to receive the SIB1 CORESET based on a reception scheme of theSS/PBCH block.